Troubleshooting

This is a list of common JavaScript errors, they cause and possible solution:
The errors described here are formatted the same way Internet Explorer 5.5 does.
For other versions or for Navigator, you should get very similar error reports.

'mFrame.document.all[...].style' is null or not an object

Description: This error is only caused when the menus were not rendered into the page and the scripts cannot find the menus object.
If you're implementing for frames, it is most likely that you haven't attached the loader code into the pages that will display the menus.

Solution: Remember that when using frames you must attach two files, one for the hotspots (the *menu.js files) and another for the menus (frames.js). Read this section of the help for more information. If you have attached the loader code for the frames.js file and you're still getting this error check that you have specified the correct parameters for the Root Web path and the Destination Folder. If one of these parameters is incorrect the page will not load the frames.js file. You could can check if the path is correct by opening the hRef.txt file and verifying that DHTML Menu Builder has generated a valid path to the file.

Another, cause of this problem may be that the code in your hotspots is outdated. If for example you have renamed a group, you should re-attach the code to your hotspots, otherwise, the trigger code in your hotspots will still be trying to display a group that no longer exists.

Access is denied or Permission denied

Description: If you get this error when trying to open a menu by hovering over a hotspot is because the document loaded into the menus frame is from a different domain than the hotspot's. Read this article for more information.

Solution: All your target files must be in the same domain.

IE is undefined or NS is undefined

Description: Right after the page loads, you get an error saying that IE or NS is undefined. This means that some part of the scripts tried to use the IE or NS variable and these didn't exists or where not initialized.

Solution: Your .js file(s) could not be loaded. This has usually two causes:

  1. You Root Web/Destination Folder paths are incorrect. Check that these parameters are correct.
  2. You haven't attached the hotspots using the HotSpot Editor. Remember that when attaching the code to hotspots using the HotSpot Editor it will also include the loader code for your .js files

Object Expected

Description: When you try to display a menu by hovering over a hotspot you get an Object Expected error. This means that the scripts made a call to a function that could not be located.

Solution: The attached code to the hotspots may be outdated. Re-run the hotspot editor and reattach the hotspots.

This is a list of common errors while using DHTML Menu Builder, they cause and possible solution:

An unexpected error has occurred while creating the HotSpots

Description: When you click the Save button on the HotSpot Editor you get the described error.

Solution: The HotSpot Editor needs to work over fully constructed HTML documents. So the file specified in the Project Properties as the one that contains the hotspots should have both, the opening and closing <html> and <body> tags. 

The best way to find solutions to the most common problems is by:

Problems while using the DHTML Menu Builder

If you get a run-time error while using the editor, please use our online support form and send: